<ui:composition xmlns="http://www.w3.org/1999/xhtml"
	xmlns:h="http://java.sun.com/jsf/html"
	xmlns:f="http://java.sun.com/jsf/core"
	xmlns:ui="http://java.sun.com/jsf/facelets"
	template="adminTemplate.xhtml">




	<ui:define name="pageIntro">
		<h2>Create an Action Path</h2>
		<p class="lftText">Use this form to create an <span>action
		path</span>.<br />
		Before understanding <span>action-path</span>s we should understand
		what <span>action</span>s are. Actions are step in a life of an <span>issue</span>.
		Let's assume that you use weebill to track bugs of a software project.
		You should have steps such "Open","Under
		Development","Resolved","Closed" or "Re-opened". Each of these steps
		are called <span>"Action"</span>'s. <br />
		Group of actions are called <span>"action-path"</span>'s. So in fact a
		bug tracking is an action-path. Another example for action-path can be
		a "Feature Request". So action-path<br />
		You can add listeners to start and end of actions while creating or
		editing the action path element. Action's are performed by users. So
		you should also select the roles that can perform this kind of action
		while editing the action-path like listeners.</p>
	</ui:define>

	<ui:define name="mainForm">
		<h:form id="crtActForm">
			<h:panelGrid columns="2">

				<h:outputLabel for="crtActPathName" value="Name"></h:outputLabel>
				<h:inputText id="crtActPathName"
					value="#{createActionPath.actionPath.name}"></h:inputText>

				<h:outputLabel for="crtActPathDescription" value="Description"></h:outputLabel>
				<h:inputText id="crtActPathDescription"
					value="#{createActionPath.actionPath.description}"></h:inputText>

			</h:panelGrid>
			<h:commandButton id="crtActPathSbt" value="Save"
				action="#{createActionPath.save}"></h:commandButton>
		</h:form>
	</ui:define>
</ui:composition>
